﻿<?xml version="1.0" encoding="utf-8"?>
<developerWhitePaperDocument
  xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5"
  xmlns:xlink="http://www.w3.org/1999/xlink">

  <!--
  <summary>
    <para>Optional summary abstract</para>
  </summary>
  -->

  <byline>
    <para>Welcome to the home of the Workflow Designers for Windows SharePoint Services 3.0.</para>
  </byline>

  <date>
    <!--<para>Date</para>-->
  </date>

  <summarySection>
    <content>
    <para>TODO: focus on the overall motivation of the toolkit.  Focus on ease of use and how it's modeled after InfoPath Forms</para>
      <para>
        Quote of the day: <phrase>"Having this framework at my disposal, including the new design time support, makes life much better for me."</phrase>
      </para>
      <para>This documentation is a work in progress.  While it's being worked on, check on the following blogs to find out more information about how to use the project.</para>
      <para>
        Wouter van Vugt's Blog -
        <externalLink>
          <linkText>http://blogs.code-counsel.net/Wouter/default.aspx</linkText>
          <linkAlternateText>http://blogs.code-counsel.net/Wouter/default.aspx</linkAlternateText>
          <linkUri>http://blogs.code-counsel.net/Wouter/default.aspx</linkUri>
        </externalLink>
      </para>
      <para>
        Chris Predeek's Blog -
        <externalLink>
          <linkText>http://predeekc.spaces.live.com/default.aspx</linkText>
          <linkAlternateText>http://predeekc.spaces.live.com/default.aspx</linkAlternateText>
          <linkUri>http://predeekc.spaces.live.com/default.aspx</linkUri>
        </externalLink>
      </para>
    </content>
  </summarySection>

  <!-- <downloadCenterLink>Optional info about downloadable content</downloadCenterLink> -->

  <!-- <appliesTo>Optional "applies to" info</appliesTo> -->

  <!-- <contents>Optional contents info</contents> -->

  <introduction>
    <!-- Uncomment this to generate an outline of the section and sub-section
         titles.  Specify a numeric value as the inner text to limit it to
         a specific number of sub-topics when creating the outline.  Specify
         zero (0) to limit it to top-level sections only.  -->
    <!-- <autoOutline /> -->

  </introduction>

  <!-- Add one or more top-level section elements.  These are collapsible.
       If using <autoOutline /> tag, add an address attribute to identify
       it so that it can be jumped to with a hyperlink. -->
  <section address="Overview">
    <title>Project Overview</title>
    <content>
      <para>The tooling provides rapid workflow development for the Windows SharePoint Services 3.0 platform, comparable to the InfoPath based design methodology used with SharePoint Server. In the toolset you will find all the components that you need to bring your workflows to the next level. Use the Visual Studio templates to easily create new workflow forms. Derive from the base classes to focus on the business at hand without the need to write SharePoint specific infrastructure, or make your workflow forms designable by using the hosted form infrastructure. As a bonus the first building blocks for bulk-task operations is also provided.</para>
      <mediaLink>
        <image placement="center" xlink:href="218620ac-01eb-4dec-bdd8-e5d57aaff694"/>
      </mediaLink>
      <para>You can use the tools in two ways. Either you create a full form (ASPX page) deriving from our base classes, or you use the hosted form control approach, which provides greater ease and flexibility. When using the hosted controls the ASPX page is provided by the tooling.</para>
      <mediaLink>
        <image placement="center" xlink:href="0068e671-d00b-4aec-9719-18700f453c9b"/>
      </mediaLink>
    </content>
  </section>

  <!-- <codeExample>Optional code example.</codeExample> -->

  <conclusion>
    <content>
      <para>Conclusion content</para>
    </content>
  </conclusion>

  <relatedTopics>
    <!-- One or more of the following:
         - A local link
         - An external link
         - A code entity reference

    <link xlink:href="Other Topic's ID">Link text</link>
    <externalLink>
        <linkText>Link text</linkText>
        <linkAlternateText>Optional alternate link text</linkAlternateText>
        <linkUri>URI</linkUri>
    </externalLink>
    <codeEntityReference>API member ID</codeEntityReference>

    Examples:

    <link xlink:href="00e97994-e9e6-46e0-b420-5be86b2f8278">Some other topic</link>

    <externalLink>
        <linkText>SHFB on CodePlex</linkText>
        <linkAlternateText>Go to CodePlex</linkAlternateText>
        <linkUri>http://www.codeplex.com/SHFB</linkUri>
    </externalLink>

    <codeEntityReference>T:TestDoc.TestClass</codeEntityReference>
    <codeEntityReference>P:TestDoc.TestClass.SomeProperty</codeEntityReference>
    <codeEntityReference>M:TestDoc.TestClass.#ctor</codeEntityReference>
    <codeEntityReference>M:TestDoc.TestClass.#ctor(System.String,System.Int32)</codeEntityReference>
    <codeEntityReference>M:TestDoc.TestClass.ToString</codeEntityReference>
    <codeEntityReference>M:TestDoc.TestClass.FirstMethod</codeEntityReference>
    <codeEntityReference>M:TestDoc.TestClass.SecondMethod(System.Int32,System.String)</codeEntityReference>
    -->
  </relatedTopics>

  <!-- <additionalInformation>Optional additional info</additionalInformation> -->

  <!-- <authorBio>Optional author bio</authorBio> -->

</developerWhitePaperDocument>
